Skip to content

catalogue: add com.github.asetapen.linux-gpu-monitor plugin#12

Closed
asetapen wants to merge 1 commit intoOpenActionAPI:mainfrom
asetapen:feature/linux-gpu-monitor
Closed

catalogue: add com.github.asetapen.linux-gpu-monitor plugin#12
asetapen wants to merge 1 commit intoOpenActionAPI:mainfrom
asetapen:feature/linux-gpu-monitor

Conversation

@asetapen
Copy link
Copy Markdown

Summary

  • Added com.github.asetapen.linux-gpu-monitor plugin
  • Displays GPU utilization, temperature, memory, and power on your Stream Deck
  • Used format_icons before committing

@nekename
Copy link
Copy Markdown
Member

Thanks for the PR @asetapen. Could you explain what features this plugin provides over the already published https://marketplace.tacto.live/plugin/com.victormarin.graphs plugin?

@asetapen
Copy link
Copy Markdown
Author

asetapen commented Apr 3, 2026

Thanks for the PR @asetapen. Could you explain what features this plugin provides over the already published https://marketplace.tacto.live/plugin/com.victormarin.graphs plugin?

Glad to contribute @nekename - OpenDeck is such a dream to work with.

The https://marketplace.tacto.live/plugin/com.victormarin.graphs plugin (which is fantastic BTW) only supports GPU temperature and GPU load. This plugin also supports GPU VRAM usage and GPU power usage. It's been helpful to have these for heavy GPU workloads.

@nekename
Copy link
Copy Markdown
Member

nekename commented Apr 3, 2026

Considering that your plugin is also written in Rust, I'd like to ask if you could consider contributing VRAM and power support to the existing Graphs plugin? This reduces fragmentation, the number of plugins that a user has to install and have running, and enables both to benefit from the same shared feature updates to graph display, etc.

@asetapen
Copy link
Copy Markdown
Author

asetapen commented Apr 4, 2026

Closing in favor of contributing these features upstream to the existing Graphs plugin per maintainer request (PR9 in opendeck-graphs). Happy to have the features in the ecosystem either way, though I'd encourage considering a more permissive submission policy in the future to reduce the barrier for new contributors.

@asetapen asetapen closed this Apr 4, 2026
@nekename
Copy link
Copy Markdown
Member

nekename commented Apr 4, 2026

Thank you, I think that's the right decision. Although I welcome the addition of new plugins, I'd rather improve performance, ease of use and overall shared functionality by combining very related things into shared plugins. It's all a big open source community so it's easy for us to work together

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants